Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

strict elemental setup #2201

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

frelon
Copy link
Contributor

@frelon frelon commented Oct 2, 2024

  • Use --strict flag in elemental-setup services
  • Set SilenceUsage for run-stage command

@frelon frelon requested a review from a team as a code owner October 2, 2024 11:40
The default behavior has been to hide any errors and only log warnings.
Using the --strict flag will ensure any yip errors are actually
reported.

Signed-off-by: Fredrik Lönnegren <[email protected]>
This ensures we do not show the usage text for errors caught during yip
execution.

Signed-off-by: Fredrik Lönnegren <[email protected]>
@frelon frelon enabled auto-merge (rebase) October 2, 2024 12:03
Copy link
Contributor

@davidcassany davidcassany left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be nice having some integration tests for that. What about setting some cloud-config in installation tests we know it will fail, so that we can check it still boots but on a degraded state, as some elemental-setup-* service failed. Even more, ideally we should be capable to see the failure in journalctl.

Alternatively, we also use such a process for the fallback test. Imagine we set a health check test that reports error if systemd is on degraded state.

Essentially, we should define the behavior we expect on a cloud-config failure and then add an integration tests to exercise it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants